Runtime installation directory reference
In this topic, you can find information about the installation directories for local runtimes.
note
Some assets for clustered runtimes can and should be configured to use local node storage. Refer to Runtime cluster and runtime cloud local storage for further details.
Boomi Support can use the directories noted in the Description column in the following table for troubleshooting.
caution
Unless specifically instructed to do so by documentation or Support, do not modify files in these directories.
| Directory | Description | Life span | How created | Contains customer data? |
|---|---|---|---|---|
<root> | Runtime installation root directory. Includes uninstall.exe. | Permanent | Upon install | No |
| accounts | (Runtime cloud only) List of tenant subdirectories for multi-tenant, runtime clouds. Each tenant has its own copy of data, process run history, process configuration, and related directories. Important for troubleshooting. | Permanent | Upon account attachment | Yes |
| accounts-deleted | (Runtime cloud only) List of recently deleted runtime cloud account attachments. | Purged periodically | Upon deleting account attachments | No |
| as2-mdn | Staging area for AS2 asynchronous MDN messages. | Momentary (consumed immediately) | Upon AS2 process run with asynchronous MDN enabled | Yes |
| auth | Cache for OAuth 2.0 tokens. | Permanent | Upon token generation | Yes |
| bin | Runtime executables and JVM configuration files, including: - atom.exe (Windows) - atomdesktop.exe (Windows desktop mode) - atom.sh (Linux) - restart.<ps1 | sh> • vmoptions (JVM settings) - error.log - output.log Additional runtime cluster and runtime cloud files include: - node-install.<ps1 | sh><br />- procrunner*.<bat | ps1 | sh> (vmoptions for forked execution)- procbrowser*.<bat | ps1 | sh> (vmoptions for launching the browse of connector operations that run in forked executions)- procworker*.<bat | ps1 | sh> (vmoptions for execution worker JVMs)Important for troubleshooting. | Permanent | Upon install | No |
| bounds | (basic runtimes, runtime clusters, runtime clouds) Lock file for Singleton Listen operations. - File locks for multi-tenant Clouds appear in an account subdirectory. The account identifier deploying the listener identifies the subdirectory. - File locks for single-tenant basic runtimes and runtime clusters appear in the root bounds directory and do not create an account subdirectory. - A unique number identifies the lock file. For example, e3d5531c-40fb-44c9-b813-0e11399660cf_275.1.lck | Purged automatically | Upon the bounded service manager starting | No |
| component | Transient XML metadata for components that ran in test mode or deployed to the runtime. | Runtime Purge Schedule | When test mode runs or deployment | Yes (encrypted passwords) |
| conf | Additional application configuration files, including: - container.properties, - /limits (attachment quotas for runtime clouds). The user interface is the preferred method for updating Properties Panel and Attachment Quotas Tab. Important for troubleshooting. | Permanent | Upon install | No |
| connector | Connector libraries It contains only those connectors required by processes that ran on this runtime. When needed, new connectors download automatically. Important for troubleshooting. | Permanent | Upon the first process run requiring a given connector | No |
| counter | Property files containing the next values for custom counters and trading partners. Modify counter values through the Runtime Management user interface only. | Permanent | Upon first use of a counter parameter or trading partner | No |
| data | Document data files used during process runs and subsequent document data viewing. You can change the directory structure of /data to accommodate more files. If you enable processed document archiving, when purging processed documents from /data, they are stored in a designated archive directory. | Runtime purge schedule | When running every process | Yes |
| doc | (Windows installation only) Start menu links to documentation. | Permanent | Upon install | No |
| doccache | Temporary directory for the Document Cache component. Typically empty except when running processes. | Single execution | When running processes that use the document cache | Yes (temporarily) |
| cached_scripts | Store compiled groovy scripts from execution of custom scripting | Runtime purge schedule | When execution | Yes |
| endorsed | Additional runtime library files. | Permanent | Upon install | No |
| execution | Run artifacts such as process and document logs, in the following subdirectories: - /<root> (persisted process properties by component ID)- /current (artifacts for in-progress runs; moved to /history upon completion)- /error (metadata regarding failed process runs; internal use only) - /history (historical run artifacts by date) - /recovery (temporary state of abnormally terminated process runs; used for cleanup) | Runtime purge schedule | When every process runs | Yes (run history) |
| .install4j | Installation artifacts. Includes inst_jre.cfg. Important for troubleshooting. | Permanent | Upon install | No |
| jre | (Optional) Local copy of the Java runtime if you had the installer or upgrader install its own copy of Java. | Permanent | Upon install | No |
| lib | Core runtime libraries. | Permanent | Upon install | No |
| logs | Daily logs, including: - container log - HTTP shared server log (including all inbound web services requests) - local user logs Important for troubleshooting. | Runtime purge schedule | Daily while runtime is running | No |
| message | Staging area for messages being exchanged with the platform, including: - Runtime status - run metadata - test mode results - UI-related information | Momentary (consumed immediately) | Upon every process run | No |
| plugins | Additional configuration and deployment artifacts for optional functionality such as the shared web server, API components, and Master Data Hub universes. | Permanent | Upon deployment of given functionality | No |
| process | List of processes attached or deployed to the runtime. | Permanent | Upon process attachment or deployment | No |
| processes | Deployment versions of component XML for processes and their dependent components. | Permanent | Upon process attachment or deployment | Yes (encrypted passwords) |
| queue | Persisted Atom queue contents. Contains pointers to document data that resides in the /data directory (not the data itself). | Runtime purge schedule (not affected by Purge Immediately) | Upon the first process run requiring the Atom Queue connector | Yes (for low latency executions) |
| resources | Independently deployed components, such as certificates and process routes. | Permanent | Upon deployment | No |
| settings | Extension values for deployed processes. Configure Process Extensions in the user interface. | Permanent | When configuring runtime or environment extensions | Yes (encrypted passwords) |
| settings-test | Extension values for test-mode processes. Setting Extension Values for Use in Test Mode are set in the user interface. | Permanent | Upon configuring test-mode extensions | Yes (encrypted passwords) |
| tmp | Temporary files for the runtime, including artifacts from when the process runs. | Runtime purge schedule | Upon every process run | Yes |
| tmpdata | Temporary files for process runs when Purge Data Immediately is turned on. | Single run | Upon every process run | Yes (but purged immediately) |
| update | Temporary space for applying runtime executable updates. | Temporary (during update only) | Upon runtime executable updates | No |
| userlib | (Optional) Additional libraries (such as third-party JAR files) for custom scripting and certain types of connectors. You can create Custom Library components that reference JAR files. When you deploy those components, Integration deploys the JAR files to /userlib or an appropriate subdirectory, such as /script or /database. Integration creates the directory if it does not exist.Important for troubleshooting. | Permanent | Created as needed for custom scripting libraries and connector drivers | No |
| work | Working copies of libraries loaded into memory at runtime, as well as some history run artifacts, including: - /as2 (AS2 artifacts, including inbound and outbound raw MIME messages and synchronous MDNs)- /cdc (change data capture, which are snapshots of the Find Changes step) | Permanent (except for /as2, which is subject to the runtime purge schedule) | Upon runtime startup and process runs | Yes |
